Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1138

reference
416-tree-1
name
1138
tree-preservation-order

undefined

416-tpo-1
uprn
address-text
point
POINT (-1.014924 50.892337)
geometry
MULTIPOLYGON (((-1.014881 50.892333,-1.014883 50.892341,-1.014889 50.892349,-1.014899 50.892355,-1.014910 50.892359,-1.014924 50.892360,-1.014937 50.892359,-1.014949 50.892355,-1.014958 50.892349,-1.014964 50.892342,-1.014967 50.892333,-1.014965 50.892325,-1.014959 50.892318,-1.014950 50.892311,-1.014925 50.892306,-1.014911 50.892307,-1.014899 50.892311,-1.014890 50.892317,-1.014884 50.892324,-1.014881 50.892333)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL